Skip to main content

This is a new service – your feedback will help us to improve it.

Royal Borough of Kingston upon Thames

Article 4 direction area

There is a problem

  • 114 issue of type invalid category value

Seething Wells Filter Beds

reference
112
name
Seething Wells Filter Beds
article-4-direction
112
permitted-development-rights

undefined

Removes permitted development rights to erect fencing, gates and other means of enclosure on the site.
uprns
address-texts
geometry
MULTIPOLYGON (((-0.312043 51.396632,-0.312152 51.396688,-0.312401 51.396809,-0.312508 51.396865,-0.312528 51.396874,-0.312537 51.396880,-0.312715 51.396787,-0.312944 51.396648,-0.312997 51.396613,-0.313346 51.396369,-0.313352 51.396373,-0.315849 51.394608,-0.315936 51.394548,-0.316097 51.394431,-0.317106 51.393714,-0.317422 51.393499,-0.317436 51.393462,-0.317415 51.393430,-0.316667 51.392887,-0.316130 51.393146,-0.315671 51.393400,-0.315304 51.393607,-0.315275 51.393626,-0.315207 51.393665,-0.313873 51.394473,-0.313706 51.394576,-0.313473 51.394725,-0.313354 51.394805,-0.313210 51.394909,-0.313048 51.395036,-0.312944 51.395125,-0.312847 51.395211,-0.312600 51.395447,-0.312003 51.396039,-0.311624 51.396427,-0.312043 51.396632)))
point
POINT (-0.314467 51.394871)
notes
Article 4 Direction at Seething Wells Filter Beds
entry-date
2021-04-14
start-date
2020-10-03
end-date

How to fix this issue

Your data is missing a permitted-development-rights.

The article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve Royal Borough of Kingston upon Thames’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL